Parsing the error code in the responses

Parsing for error codes

In the document’s error code tables, in addition to the error codes, the associated messages and explanations are also given. Both pieces of information are human-understandable translations of the machine-readable error codes.

We recommend that the messages of the responses should not be evaluated automatically, as the error texts can be subject to constant changes. This also applies to messages that contain a dynamic error text in addition to the static error text.

Limit your automated evaluation of an error to the error code only.

Example error response in K/V format to a CREATE request

RESULT: success ERROR: 53300102912 Nameserver error [ERROR: 901 Unexpected RCODE (1)] WARNING: 33300102900 The provided DNS data are not acceptable. Domain "Status" is "failed". [2021-08-20T13:06:05+02:00] STID: 7767b575-eace-11eb-9ccc-0141a1811e3e CTID: Test#1626945804-27198095-0

Example error response in XML format to a CREATE request

<?xml version="1.0" encoding="UTF-8"?> <registry-response xmlns="http://registry.denic.de/global/3.0" xmlns:tr="http://registry.denic.de/transaction/3.0">  <tr:transaction>   <tr:stid>1ebc1fb2-eace-11eb-9ccc-0141a1811e3e</tr:stid>   <tr:ctid>Test#1626945656-27198094-0</tr:ctid>   <tr:result>success</tr:result>   <tr:message level="error" code="53300102912">    <tr:text>Nameserver error</tr:text>    <tr:argument>ERROR: 901 Unexpected RCODE (1)</tr:argument>   </tr:message>   <tr:message level="warning" code="33300102900">    <tr:text>The provided DNS data are not acceptable. Domain "Status" is "failed".</tr:text>    <tr:argument>2021-08-20T13:06:05+02:00</tr:argument>   </tr:message>  </tr:transaction> </registry-response>